Main ----- Copyright Up Previous Next

What happened to the attitude you used to have at school
What happened to the attitude when you broke all the rules

(The Farm, "Groovy Train")

Messages

hsc is able to produce lots of different warnings and errors when parsing html-files. The appearence looks something like:
file (line#, colum#): class and message-id: message
with
  file           input file that caused message
  line#,         position in input file that caused error
  colum#
  class          one of Note, Warning, Error or Fatal error
  message        message text
This can be modified using the CLI-option MSGFORMAT.

Message Classes

Note is a message only for the users information. It can be suppressed using IGNORE.

Bad style informs the user that his altough legal html-code includes constructs that indicate a bad style. It can be suppressed using IGNORE.

Portability problem informs the user that his altough legal html-code includes constructs can lead to problems on old or buggy browsers. It can be suppressed using IGNORE.

Warning tells you that your source includes some problematic parts, that can lead to problems with several browsers. It can be suppressed using IGNORE.

Error indicates that there is something wrong with your html-source. No output is written.

Fatal error tells you that something terrible has happened and there is no way to continue the conversion. No output is written.


Note: I've already started to collect the messages, but this list is not yet complete.

warning 1: unable to open project-file
The project-file specified could not been open. This indicates no problem, if you specified a project-file using PRJFILE the first time; it will be created automatically after the html-object has successfully been processed.

fatal error 2: project-file corrupt
The data found in the project file are not of the required form. Most likely, the file-format-version is outdated. Remove the old file, hsc will create a new one next time it is invoked.

fatal error 3: unexpected end of file
There are still characters to be read from input, but the file already ends; hsc tells you what it still expects to come.

error 4:
Undocumented.

error 5:
Undocumented.

fatal error 6: can not open file for input
An input file could not been opened. A more detailed message that tells you why is displayed, too.

error 7:
Undocumented.

error 8:
Undocumented.

error 9:
Undocumented.

bad style 10: "click here" syndrome detected
A keyword defined with the special attribute HSC.CLICK-HERE has been found within the text inside an anchor specification.

Ok, now again in english: you used some term like "Click here" inside the text describing a link. This is very clumsy and should be avoided; see Composing Good HTML for details.

error 11: unknown tag <tag>
You refered to an unknown tag or macro.

error 12: tag <tag> occured too often
A tag that is expected to occure only once appeared at least twice. Remove all unneccessary occurences of the tag.

warning 13: unmatched end-tag <tag>
You called a end-tag without using the corresponding start-tag before.

warning 14: illegal end-tag nesting
A end-tag appeard where a different end-tag was expected to appear before. Example: instead of
        <B><I>bold and italic</B></I>
you should write
        <B><I>bold and italic</I></B>

warning 15: required tag <tag> missing
A tag that is required for every document is missing.

warning 16: end-tag <tag> missing
You called an start-tag, but didn't end it. Insert the required end-tag.

error 17:
Undocumented.

warning 18: unknown entity
You used an entity, that hsc doesn't know. This can happen if you made a typo, or the entity has not been defined within hsc.prefs.

error 19:
Undocumented.

error 20: reference to unknown attribute
You referered to an attribute that doesn't exist at all.

warning 21: path to URI not found: file
A tag points to a local resource that doesn't exist.

warning 22: argument without quote
You passed a value to an attribute, but did not embed it into single or double quotes. This can lead to problems with older browsers.

error 23: empty reference to attribute attrib
An attribute referes to an attribute that has been defined, but no value has been set for. Usually, you try to refer to an attribute inside a macro, that no value has been passed to within the call of the macro.

error 24:
Undocumented.

bad style 25: <BLINK> sucks
Some browser support the non-html-tag <BLINK>. It is used to make text blinking, which annoys many users. Additionally, most of them don't know how to configure their browser that it doesn't blink, so you really should avoid it.

error 26:
Undocumented.

error 27:
Undocumented.

error 28:
Undocumented.

error 29:
Undocumented.

error 30: unmatched ">"
A "greater than" sign appeared inside the text. You should write "&gt;" instead. This can also happen, if you made an error calling a tag, and hsc's parser couln't recover.

error 31:
Undocumented.

error 32:
Undocumented.

error 33:
Undocumented.

error 34:
Undocumented.

error 35: unknown value value for enumerator attribute attrib
You tried to set an enumerator to a value it doesn't support.

error 36:
Undocumented.

warning 37: tag <tag> is obsolete
The tag was defined within some old html-version, but should not be used any more (eg. <LISTING>).

warning 38: tag <tag> is only used by jerks
This tag is no legal html-tag and is only supportet by special browsers.

error 39:
Undocumented.

error 40:
Undocumented.

error 41:
Undocumented.

error 42:
Undocumented.

error 43: unknown attribute option option
You defined a new attribute, but used an option that is unknown.

error 44: required attribute attrib missing
An attribute that is required has not been set within the call of a tag or macro.

error 45:
Undocumented.

note 46: replaced char by entity
Informs you that a special character (non-7-bit-ASCII) has been replaced by it's corresponding entity.

error 47:
Undocumented.

error 48:
Undocumented.

error 49:
Undocumented.

error 50:
Undocumented.

error 51:
Undocumented.

error 52:
Undocumented.

error 53:
Undocumented.

warning 54: calling external command returned value
You've called a shell-command using <$exec> and it returned a value unequal to zero, which usually denotes an error while processing the command. For error analysis, look at the output that the command (hopefully) has made.

error 55:
Undocumented.

error 56:
Undocumented.

error 57:
Undocumented.

port 58: icon-entity <entity> found
Icon-entities are (not-yet) widly supported.

error 59:
Undocumented.

error 60: tag <tag> must be inside tag <tag>
Before you are allowed to use the first tag, the second tag has to occure before. Example: <INPUT> may only occure inside <FORM>.

error 61: tag <tag> not allowed within tag <tag>
A tag occures inside another tag that doesn't allowe this. For example, you can't recursively use <A> inside <A>.

error 62: no attributes allowed for end-tags
You tried to pass values to a end-tag or macro. If you need an attribute for a end-macro only, you still have to define and pass it within the start-macro; the end-macro will have access to all these attributes and its values.

warning 63: redefinance of attribute attrib
You redefined an alredy existing attribute. If this occures during the definition of a new macro, you just tried to give two arguments the same name.

error 64:
Undocumented.

error 65:
Undocumented.

error 66: illegal end-tag
You tried to use a simple tag as a container, for example </IMG>

error 67:
Undocumented.

note 68: unknown filetype
hsc could not determine the size of a link destination.

error 69: illegal entity definition
Somethings wrong with a <$deftag> or <$deficon> call.

error 70:
Undocumented.

error 71:
Undocumented.

warning 72: illegal color value
A color value must fit the template `#rrggbb' or be one of the values declared in the special attribute HSC.COLOR-NAMES defined in hsc.prefs

error 73:
Undocumented.

error 74:
Undocumented.

error 75:
Undocumented.

bad style 76: frames are disgusting
This message should need no comment; anyway, read Why Frames Suck for more details.

error 77:
Undocumented.

bad style 78: succeeding white-space for tag <tag>
See below.

bad style 79: preceding white-space for end-tag <tag>
These two messages point out that instead of (read the underscore (`_') as a blank)
<STRONG>__important__</STRONG>
you should better use
<STRONG>important</STRONG>
It only affects the tags <A>, <TITLE>, headings and physical/locigal styles.

Thomas Aglassinger (agi@giga.or.at), 30-Sep-1996